docs(bot-detection): add GPU Acceleration to Kernel Features That Help#346
Conversation
Surface the bot-detection benefit of GPU-enabled browsers for login flows on sites that fingerprint rendering output (canvas/WebGL).
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Drop the GPU bullet from the Managed Auth feature list — it belongs under Kernel Features That Help on the bot-detection overview, where the other anti-detection levers (stealth, proxies, profiles, computer controls) are listed.
ulziibay-kernel
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This PR only modifies documentation (bot-detection overview), not API endpoints or Temporal workflows in packages/api/cmd/api/ or packages/api/lib/temporal. To monitor this PR anyway, reply with |
There was a problem hiding this comment.
Risk assessment: Very Low.
The PR only adds a short GPU Acceleration section to browsers/bot-detection/overview.mdx. This is a small documentation-only change with no application code, configuration, infrastructure, generated assets, or navigation structure modified. I found no CODEOWNERS file requiring owner review.
The current PR head is already approved, so I’m not adding another approval.
Sent by Cursor Automation: Assign PR reviewers
3 participants
Summary
Adds a GPU Acceleration section under "Kernel Features That Help" on the bot-detection overview, alongside Stealth Mode, Configurable Proxies, Profiles, Browser Pools, Playwright Execution, and Computer Controls.
Many detection systems fingerprint canvas/WebGL rendering output and cross-check it against the claimed GPU. Software-rendered (SwiftShader) browsers produce pixel hashes that don't match any real consumer GPU — a strong bot signal on sites with rendering-based fingerprinting. GPU-enabled Kernel browsers render through real hardware, producing output consistent with a normal user's device.
Links to the existing
/browsers/gpu-accelerationpage so users can opt in.(Earlier draft of this PR put the bullet on the Managed Auth overview — moved it to bot-detection overview where it sits with the other anti-detection levers.)
Test plan
browsers/bot-detection/overview.mdxlocally and confirm the new section + link render correctly/browsers/gpu-accelerationlink resolvesNote
Low Risk
Low risk documentation-only change that adds a new section and link; main risk is incorrect/misleading copy or a broken
/browsers/gpu-accelerationlink.Overview
Adds a new GPU Acceleration entry under Kernel Features That Help in
browsers/bot-detection/overview.mdx, explaining how hardware-backed rendering can reduce canvas/WebGL fingerprint mismatches and linking to/browsers/gpu-accelerationfor details.Reviewed by Cursor Bugbot for commit 9882f89. Bugbot is set up for automated code reviews on this repo. Configure here.